configure ip-security dhcp-bindings storage

configure ip-security dhcp-bindings storage [write-interval minutes | write-threshold num_changed_entries]

Description

Configures DHCP (Dynamic Host Configuration Protocol) bindings file storage upload variables.

Syntax Description

minutes Specifies the number of minutes for the write interval.
num_changed_entries Specifies the limit for the write threshold.

Default

The default write threshold is 50 entries; the default write interval is 30 minutes.

Usage Guidelines

This commands allows you to configure the upload variables for the DHCP bindings file that you created with the command configure ip-security dhcp-bindings storage filename name and specified the location of with the command configure ip-security dhcp-bindings storage location server [primary | secondary] ip_address |hostname]{vrvr-name} tftp.

For redundancy, the DHCP bindings file is uploaded to both the primary and the secondary server. The failure of one upload (for example, due to a TFTP server timeout) does not affect the upload of any other.

When the maximum file size limit is reached, no additional DHCP bindings can be uploaded until one of the older bindings is removed.

The point at which DHCP bindings can be uploaded can be configured to work in one of the following ways:
  • Periodic upload: Upload every N minutes, provided that DHCP bindings have changed since the last upload.

  • Upload based on number of yet-to-be uploaded entries: Allows you to configure the maximum number of changed entries that are allowed to accumulate before being uploaded.

The write interval is configurable from 5 minutes to 1 day, with a default value of 30 minutes. The default value of the write threshold is 50 entries, with a minimum of 25 and maximum of 200.

Additions and deletions are considered changes, but updates are not, which means that DHCP renewals of existing leases are not counted.

By default, the write interval is in effect, but not the write-threshold. You may change whichever of these you wish by explicitly configuring the value.

History

This command was first available in ExtremeXOS 12.1.

Platform Availability